<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"  lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
	
	<meta name="generator" content="MediaWiki 1.13.2" />
		<meta name="keywords" content="hcard,hcard,adr,buttons,geo,geo-brainstorming,hCard-to-do,hReview,hcalendar,hcard-advocacy,hcard-authoring" />
		<link rel="shortcut icon" href="/favicon.ico" />
		<link rel="search" type="application/opensearchdescription+xml" href="/wiki/opensearch_desc.php" title="Microformats Wiki (en)" />
		<link rel="alternate" type="application/rss+xml" title="Microformats Wiki RSS Feed" href="http://microformats.org/wiki/index.php?title=Special:RecentChanges&amp;feed=rss" />
		<link rel="alternate" type="application/atom+xml" title="Microformats Wiki Atom Feed" href="http://microformats.org/wiki/index.php?title=Special:RecentChanges&amp;feed=atom" />
	<link rel="stylesheet" type="text/css" href="/wiki/skins/common/shared.css" />		
	<link rel="stylesheet" type="text/css" href="/wiki/skins/Microformats/microformats.css"/>

	<style type="text/css">/*<![CDATA[*/
@import "/wiki/index.php?title=MediaWiki:Common.css&usemsgcache=yes&action=raw&ctype=text/css&smaxage=18000";
@import "/wiki/index.php?title=MediaWiki:Microformats_Wiki.css&usemsgcache=yes&action=raw&ctype=text/css&smaxage=18000";
@import "/wiki/index.php?title=-&action=raw&gen=css&maxage=18000&useskin=Microformats+Wiki";
/*]]>*/</style>
<script type= "text/javascript">/*<![CDATA[*/
var skin = "Microformats Wiki";
var stylepath = "/wiki/skins";
var wgArticlePath = "/wiki/$1";
var wgScriptPath = "/wiki";
var wgScript = "/wiki/index.php";
var wgVariantArticlePath = false;
var wgActionPaths = [];
var wgServer = "http://microformats.org";
var wgCanonicalNamespace = "";
var wgCanonicalSpecialPageName = false;
var wgNamespaceNumber = 0;
var wgPageName = "hcard";
var wgTitle = "hcard";
var wgAction = "view";
var wgArticleId = "1002";
var wgIsArticle = true;
var wgUserName = null;
var wgUserGroups = null;
var wgUserLanguage = "en";
var wgContentLanguage = "en";
var wgBreakFrames = false;
var wgCurRevisionId = "37804";
var wgVersion = "1.13.2";
var wgEnableAPI = true;
var wgEnableWriteAPI = false;
var wgRestrictionEdit = [];
var wgRestrictionMove = [];
/*]]>*/</script>

    <script type="text/javascript" src="/wiki/skins/common/wikibits.js?164"></script>
    		<script type="text/javascript" src="/wiki/skins/common/ajax.js?164"></script>
        <script type="text/javascript" src="/wiki/index.php?title=-&amp;action=raw&amp;gen=js&amp;useskin=Microformats+Wiki"><!-- site js --></script>
        	
	<title>hCard &middot; Microformats Wiki</title>
	
</head>
	<!-- TODO: Template-dervied body class: spec and draft -->
<body class="page-hcard specification">
    
    <div class="header">
            <a class="logo" href="/wiki/Main_Page">
                <img src="/wiki/skins/Microformats/images/logo.gif" alt="Microformats Wiki"/>
            </a>
        
        <ul class="nav">
            <li><a href="/" title="Microformats.org Home">Blog</a></li>
            <li class="active"><span>Wiki</span></li>
            <li><a href="/discuss" title="Microformats discussion lists">Discuss</a></li>
        </ul>
        
        <form action="/wiki/Special:Search" id="search">
            <fieldset>
            <label for="search-text">Search</label>
    	    <input id="search-text" name="search" type="text" title="Search Microformats Wiki [f]" accesskey="f" value="" />
	        <input type="submit" name="go" class="searchButton" id="searchGoButton"	value="Go" title="Go to a page with this exact name if exists" /> 
	        <input type="submit" name="fulltext" class="searchButton" id="mw-searchButton" value="Search" title="Search the pages for this text" />
	        </fieldset>
		</form>
    </div>

    <div class="content hentry">
    
	

	    <h1 class="entry-title">hCard</h1>

		<p class="sub-title"></p>

								    <!-- TODO: Jump nav -->
		    <div id="jump-to-nav">Jump to:		        <a href="#sidebar">navigation</a>, 
		        <a href="#search">search</a>
		    </div>
		        
        <div class="entry-content">
		<table id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1"><a href="#Specification"><span class="tocnumber">1</span> <span class="toctext">Specification</span></a></li>
<li class="toclevel-1"><a href="#Introduction"><span class="tocnumber">2</span> <span class="toctext">Introduction</span></a></li>
<li class="toclevel-1"><a href="#Format"><span class="tocnumber">3</span> <span class="toctext">Format</span></a>
<ul>
<li class="toclevel-2"><a href="#In_General"><span class="tocnumber">3.1</span> <span class="toctext">In General</span></a></li>
<li class="toclevel-2"><a href="#Root_Class_Name"><span class="tocnumber">3.2</span> <span class="toctext">Root Class Name</span></a></li>
<li class="toclevel-2"><a href="#Properties_and_Sub-properties"><span class="tocnumber">3.3</span> <span class="toctext">Properties and Sub-properties</span></a></li>
<li class="toclevel-2"><a href="#Property_List"><span class="tocnumber">3.4</span> <span class="toctext">Property List</span></a></li>
<li class="toclevel-2"><a href="#Property_Notes"><span class="tocnumber">3.5</span> <span class="toctext">Property Notes</span></a></li>
<li class="toclevel-2"><a href="#Singular_vs._Plural_Properties"><span class="tocnumber">3.6</span> <span class="toctext">Singular vs. Plural Properties</span></a></li>
<li class="toclevel-2"><a href="#Human_vs._Machine_readable"><span class="tocnumber">3.7</span> <span class="toctext">Human vs. Machine readable</span></a></li>
<li class="toclevel-2"><a href="#Value_excerpting"><span class="tocnumber">3.8</span> <span class="toctext">Value excerpting</span></a></li>
<li class="toclevel-2"><a href="#Property_Exceptions"><span class="tocnumber">3.9</span> <span class="toctext">Property Exceptions</span></a></li>
<li class="toclevel-2"><a href="#Organization_Contact_Info"><span class="tocnumber">3.10</span> <span class="toctext">Organization Contact Info</span></a></li>
<li class="toclevel-2"><a href="#Implied_.22n.22_Optimization"><span class="tocnumber">3.11</span> <span class="toctext">Implied "n" Optimization</span></a></li>
<li class="toclevel-2"><a href="#Implied_.22nickname.22_Optimization"><span class="tocnumber">3.12</span> <span class="toctext">Implied "nickname" Optimization</span></a></li>
<li class="toclevel-2"><a href="#Implied_.22organization-name.22_Optimization"><span class="tocnumber">3.13</span> <span class="toctext">Implied "organization-name" Optimization</span></a></li>
<li class="toclevel-2"><a href="#Tags_as_Categories"><span class="tocnumber">3.14</span> <span class="toctext">Tags as Categories</span></a></li>
<li class="toclevel-2"><a href="#type_subproperty_values"><span class="tocnumber">3.15</span> <span class="toctext">type subproperty values</span></a>
<ul>
<li class="toclevel-3"><a href="#type_with_unspecified_value"><span class="tocnumber">3.15.1</span> <span class="toctext">type with unspecified value</span></a></li>
<li class="toclevel-3"><a href="#adr_tel_email_types"><span class="tocnumber">3.15.2</span> <span class="toctext">adr tel email types</span></a></li>
</ul>
</li>
<li class="toclevel-2"><a href="#XMDP_Profile"><span class="tocnumber">3.16</span> <span class="toctext">XMDP Profile</span></a></li>
<li class="toclevel-2"><a href="#Parsing_Details"><span class="tocnumber">3.17</span> <span class="toctext">Parsing Details</span></a></li>
</ul>
</li>
<li class="toclevel-1"><a href="#Examples"><span class="tocnumber">4</span> <span class="toctext">Examples</span></a>
<ul>
<li class="toclevel-2"><a href="#Sample_vCard"><span class="tocnumber">4.1</span> <span class="toctext">Sample vCard</span></a></li>
<li class="toclevel-2"><a href="#Live_example"><span class="tocnumber">4.2</span> <span class="toctext">Live example</span></a></li>
<li class="toclevel-2"><a href="#More_Examples"><span class="tocnumber">4.3</span> <span class="toctext">More Examples</span></a></li>
</ul>
</li>
<li class="toclevel-1"><a href="#Buttons"><span class="tocnumber">5</span> <span class="toctext">Buttons</span></a></li>
<li class="toclevel-1"><a href="#Examples_in_the_wild"><span class="tocnumber">6</span> <span class="toctext">Examples in the wild</span></a></li>
<li class="toclevel-1"><a href="#Implementations"><span class="tocnumber">7</span> <span class="toctext">Implementations</span></a></li>
<li class="toclevel-1"><a href="#Copyright"><span class="tocnumber">8</span> <span class="toctext">Copyright</span></a></li>
<li class="toclevel-1"><a href="#Patents"><span class="tocnumber">9</span> <span class="toctext">Patents</span></a></li>
<li class="toclevel-1"><a href="#References"><span class="tocnumber">10</span> <span class="toctext">References</span></a>
<ul>
<li class="toclevel-2"><a href="#Normative_References"><span class="tocnumber">10.1</span> <span class="toctext">Normative References</span></a></li>
<li class="toclevel-2"><a href="#Informative_References"><span class="tocnumber">10.2</span> <span class="toctext">Informative References</span></a>
<ul>
<li class="toclevel-3"><a href="#Specifications_That_Use_hCard"><span class="tocnumber">10.2.1</span> <span class="toctext">Specifications That Use hCard</span></a></li>
<li class="toclevel-3"><a href="#Similar_Work"><span class="tocnumber">10.2.2</span> <span class="toctext">Similar Work</span></a></li>
</ul>
</li>
</ul>
</li>
<li class="toclevel-1"><a href="#Inspiration_and_Acknowledgments"><span class="tocnumber">11</span> <span class="toctext">Inspiration and Acknowledgments</span></a></li>
<li class="toclevel-1"><a href="#Notes_on_derivation_from_vCard"><span class="tocnumber">12</span> <span class="toctext">Notes on derivation from vCard</span></a>
<ul>
<li class="toclevel-2"><a href="#More_Semantic_Equivalents"><span class="tocnumber">12.1</span> <span class="toctext">More Semantic Equivalents</span></a></li>
<li class="toclevel-2"><a href="#Singular_and_Plural_derivations"><span class="tocnumber">12.2</span> <span class="toctext">Singular and Plural derivations</span></a>
<ul>
<li class="toclevel-3"><a href="#Plural_Properties_Singularized"><span class="tocnumber">12.2.1</span> <span class="toctext">Plural Properties Singularized</span></a></li>
</ul>
</li>
</ul>
</li>
<li class="toclevel-1"><a href="#Further_Reading"><span class="tocnumber">13</span> <span class="toctext">Further Reading</span></a></li>
<li class="toclevel-1"><a href="#Related_Pages"><span class="tocnumber">14</span> <span class="toctext">Related Pages</span></a></li>
</ul>
</td></tr></table><script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>
<p>hCard is a simple, open, distributed format for representing people, companies, organizations, and places, using a 1:1 representation of vCard (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>) properties and values in <a href="/wiki/semantic-xhtml" title="semantic-xhtml">semantic HTML or XHTML</a>. hCard is one of several open <a href="/wiki/microformats" title="microformats">microformat</a> standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.
</p><p>Want to get started with writing an <strong class="selflink">hCard</strong>?  Use the <a href="http://microformats.org/code/hcard/creator" class="external text" title="http://microformats.org/code/hcard/creator" rel="nofollow">hCard creator</a> to write up some contact information and publish it, or follow the <a href="/wiki/hcard-authoring" title="hcard-authoring">hCard authoring tips</a> to add hCard markup to your current contact page.
</p>
<a name="Specification"></a><h2> <span class="mw-headline"> Specification </span></h2>
<div class="vcard">
<dl><dt> <span class="role">Editor</span> 
</dt><dd> <span class="fn"><a href="/wiki/User:Tantek" title="User:Tantek">Tantek Çelik</a></span> (<span class="url"><a href="http://tantek.com/" class="external free" title="http://tantek.com/" rel="nofollow">http://tantek.com/</a></span>, and before at <a href="http://technorati.com" class="external text" title="http://technorati.com" rel="nofollow">Technorati, Inc.</a>, and at <a href="http://microsoft.com/" class="external text" title="http://microsoft.com/" rel="nofollow">Microsoft Corporation</a>)
</dd></dl>
</div>
<dl><dt> Authors</dt><dd> <a href="http://tantek.com/" class="external text" title="http://tantek.com/" rel="nofollow">Tantek Çelik</a> (affiliations above)
</dd><dd> <span class="vcard"><span class="fn"><a href="/wiki/User:Brian" title="User:Brian">Brian Suda</a></span> (<span class="url"><a href="http://suda.co.uk/" class="external free" title="http://suda.co.uk/" rel="nofollow">http://suda.co.uk/</a></span>)</span>
</dd></dl>
<dl><dt> Acknowledgments</dt><dd> See <a href="/wiki/hcard#Inspiration_and_Acknowledgments" title="hcard">acknowledgments</a>.
</dd></dl>
<p><a href="/wiki/hcard#Copyright" title="hcard">copyright</a> and <a href="/wiki/hcard#Patents" title="hcard">patents</a> statements apply.
</p>
<a name="Introduction"></a><h2> <span class="mw-headline"> Introduction </span></h2>
<p>The vCard standard (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).
</p><p>In addition, many bloggers identify themselves by name and discuss their friends and family.  With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.
</p><p>This specification introduces the <b>hCard</b> format, which uses a 1:1 representation of the properties and values of the aforementioned vCard standard, in semantic HTML.  Bloggers can both embed hCards directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCard enables applications to retrieve information directly from web pages without having to reference a separate file.
</p><p>Use the <a href="http://microformats.org/code/hcard/creator" class="external text" title="http://microformats.org/code/hcard/creator" rel="nofollow">hCard creator</a> and copy the HTML code it generates to your blog or website to publish your contact info.
</p><p>The key words "<em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em>", "<em title="MUST NOT in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST NOT</em>", "<em title="REQUIRED in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">REQUIRED</em>", "<em title="SHALL in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHALL</em>", "<em title="SHALL NOT in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHALL NOT</em>", "<em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em>", "<em title="SHOULD NOT in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD NOT</em>", "<em title="RECOMMENDED in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">RECOMMENDED</em>", "<em title="MAY in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MAY</em>", and "<em title="OPTIONAL in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">OPTIONAL</em>" in this document are to be interpreted as described in <a href="/wiki/rfc-2119" title="rfc-2119">RFC 2119</a>.
</p>
<a name="Format"></a><h2> <span class="mw-headline"> Format </span></h2>
<a name="In_General"></a><h3> <span class="mw-headline"> In General </span></h3>
<p>The vCard standard (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>) forms the basis of hCard.
</p><p>The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested HTML elements.
</p>
<a name="Root_Class_Name"></a><h3> <span class="mw-headline"> Root Class Name </span></h3>
<p>The root class name for an hCard is "vcard".  An element with a class name of "vcard" is itself called an <i>hCard</i>.
</p>
<a name="Properties_and_Sub-properties"></a><h3> <span class="mw-headline"> Properties and Sub-properties </span></h3>
<p>The properties of an hCard are represented by elements inside the hCard.  Elements with class names of the listed properties represent the values of those properties.  Some properties have sub-properties, and those are represented by elements inside the elements for properties.
</p>
<a name="Property_List"></a><h3> <span class="mw-headline"> Property List </span></h3>
<p>hCard properties (sub-properties in parentheses like this)
</p><p><b>Required:</b>
</p>
<ul><li> <b>fn</b>
</li><li> <span id="property-list-n"><b>n</b><sup style="font-size:smaller"><a href="#note1" title="">1</a></sup> (family-name, given-name, additional-name, honorific-prefix, honorific-suffix)</span>
</li></ul>
<p>Optional:
</p>
<ul><li> nickname, sort-string
</li><li> url, email (type, value), <span id="property-list-tel">tel<sup style="font-size:smaller"><a href="#note2" title="">2</a></sup> (type, value)</span>
</li><li> adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
</li><li> geo (latitude, longitude), tz
</li><li> photo, logo, sound, bday
</li><li> title, role, org (organization-name, organization-unit)
</li><li> category, note
</li><li> class, key, mailer, uid, rev
</li></ul>
<a name="Property_Notes"></a><h3> <span class="mw-headline"> Property Notes </span></h3>
<p><span id="note1"><a href="#property-list-n" title="">1. ^</a></span>: The 'n' property is <em title="OPTIONAL in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">OPTIONAL</em> if any <a href="/wiki/hcard#Implied_.22n.22_Optimization" title="hcard">implied 'n' optimization rules</a> are in effect.<br />
<span id="note2"><a href="#property-list-tel" title="">2. ^</a></span>: tel - Authors <em title="MAY in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MAY</em> follow the <a href="http://en.wikipedia.org/wiki/E.123" class="external text" title="http://en.wikipedia.org/wiki/E.123" rel="nofollow">E.123</a> standard for writing values of telephone numbers. Letter values (e.g. +1-555-FORMATS) <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> be converted to numbers. Use an <code>abbr</code> to display letters and provide a numerical value simultaneously, e.g. <code>&lt;abbr title=&quot;+15553676287&quot;&gt;+1-555-FORMATS&lt;/abbr&gt;</code>.
</p>
<a name="Singular_vs._Plural_Properties"></a><h3> <span class="mw-headline"> Singular vs. Plural Properties </span></h3>
<p>Singular properties: 'fn', 'n', 'bday', 'tz', 'geo', 'sort-string', 'uid', 'class'.  For properties which are singular, the first descendant element with that class <em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em> take effect, any others being ignored.
</p><p>All other properties <em title="MAY in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MAY</em> be plural. Each class instance of such properties creates a new instance of that property.
</p>
<a name="Human_vs._Machine_readable"></a><h3> <span class="mw-headline"> Human vs. Machine readable </span></h3>
<p>The human visible text contents of an element for a property represents the value of that property, with a few exceptions:
</p><p>If an <code>&lt;abbr&gt;</code> element is used for a property, then the '<code>title</code>' attribute (if present) of the <code>&lt;abbr&gt;</code> element is the value of the property, instead of the contents of the element, which instead provide a more human presentable version of the value.
</p><p>If an <code>&lt;a&gt;</code> element is used for one or more properties, it <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> be treated as follows:
</p>
<ol><li> For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
</li><li> For other properties, the element's content is the value of the property.
</li></ol>
<p>If an <code>&lt;img&gt;</code> element is used for one or more properties, it <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> be treated as follows:
</p>
<ol><li> For the 'photo' property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
</li><li> For other properties, the <code>&lt;img&gt;</code> element's '<code>alt</code>' attribute is the value of the property.
</li></ol>
<p>If an <code>&lt;object&gt;</code> element is used for one or more properties, it <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> be treated as follows:
</p>
<ol><li> For the 'photo' property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
</li><li> For other properties, the element's content is the value of the property.
</li></ol>
<a name="Value_excerpting"></a><h3> <span class="mw-headline"> Value excerpting </span></h3>
<p>Sometimes only part of an element which is the equivalent for a property is used for the value of the property.  This typically occurs when a property has a subtype, like 'tel'. For this purpose, the special class name "<code>value</code>" is used to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:<br />
</p><p>vCard:
</p>
<pre>
TEL;TYPE=HOME:+1.415.555.1212
</pre>
<p>hCard:
</p>
<pre>
&lt;span class=&quot;tel&quot;&gt;
 &lt;span class=&quot;type&quot;&gt;home&lt;/span&gt;:
 &lt;span class=&quot;value&quot;&gt;+1.415.555.1212&lt;/span&gt;
&lt;/span&gt;
</pre>
<p>This hCard fragment could be displayed as:
</p>
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<p><span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</p>
</div>
<p><br />
</p>
<a name="Property_Exceptions"></a><h3> <span class="mw-headline"> Property Exceptions </span></h3>
<p>vCard has several properties which either do not make sense on, or are already implied within the context of a web page.  This section explains what to (not) do with them.
</p>
<ol><li> vCard's <b>NAME</b>, <b>PROFILE</b>, <b>SOURCE</b>, <b>PRODID</b>, <b>VERSION</b> properties are defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>.  Content publishers <em title="MUST NOT in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST NOT</em> use these properties in their hCards, and as such, hCard consumers/parsers <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters <em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em> use the title of the page where the hCard is found (e.g. the <code>&lt;title&gt;</code> element in HTML documents) to construct the NAME property, <em title="MAY in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MAY</em> output a PROFILE value of "<code>VCARD</code>" per <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>, <em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em> use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly, only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a> Section 3.6.9.
</li></ol>
<a name="Organization_Contact_Info"></a><h3> <span class="mw-headline"> Organization Contact Info </span></h3>
<p>If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company, organization or place and <em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em> be treated as such. In this case the author also <em title="MUST NOT in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST NOT</em> set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers <em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em> handle the missing "N" property, in this case by implying empty values for all the "N" sub-properties.
</p>
<a name="Implied_.22n.22_Optimization"></a><h3> <span class="mw-headline"> Implied "n" Optimization </span></h3>
<p>Although vCard requires that the "N" property be present, the authors of the vCard specification (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>) themselves do not include "N" properties in their vCards near the end of the spec (p.38).  This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.
</p><p>If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property.  For "FN"s with either one word see below, and for three or more, the author <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> explicitly markup the "N", except for the organization contact info case, <a href="http://microformats.org/wiki/hcard#Organization_Contact_Info" class="external text" title="http://microformats.org/wiki/hcard#Organization_Contact_Info" rel="nofollow">see above</a> for that.
</p>
<ol><li> The content of "FN" is broken into two "words" separated by whitespace.
</li><li> The <i>first</i> word of the "FN" is interpreted as the "given-name" for the "N" property.
</li><li> The <i>second/last</i> word of the "FN" is interpreted as the "family-name" for the "N" property.
</li><li> Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".
</li></ol>
<p>This allows simplification in the typical case of people stating:
</p>
<ul><li> given-name (space) family-name
</li><li> family-name (comma) given-name
</li><li> family-name (comma) given-name-first-initial
</li><li> family-name (space) given-name-first-initial (optional period)
</li></ul>
<a name="Implied_.22nickname.22_Optimization"></a><h3> <span class="mw-headline"> Implied "nickname" Optimization </span></h3>
<p>Due to the prevalence of the use of nicknames/handles/usernames in actual content published on the Web (e.g. authors of <a href="/wiki/hReview" class="mw-redirect" title="hReview">reviews</a>), hCard also has an implied "nickname" optimization to handle this.
</p><p>Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:
</p>
<ol><li> The content of the "FN" <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> be treated as a "nickname" property value.
</li><li> Parsers <em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em> handle the missing "N" property by implying empty values for all the "N" sub-properties.
</li></ol>
<p>Though parsers <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> follow the implied nickname optimization, publishers <em title="SHOULD in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">SHOULD</em> explicitly indicate the "nickname" even in this case, e.g.:
</p>
<pre>
&lt;span class=&quot;vcard&quot;&gt;
 &lt;span class=&quot;fn nickname&quot;&gt;daveman692&lt;/span&gt;
&lt;/span&gt;
</pre>
<p>The hCard <em title="MAY in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MAY</em> have additional explicit "nickname" property values in addition to the implied nickname.
</p>
<a name="Implied_.22organization-name.22_Optimization"></a><h3> <span class="mw-headline"> Implied "organization-name" Optimization </span></h3>
<p>The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name.  Thus if an "ORG" property has no "organization-name" inside it, then its entire contents <em title="MUST in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MUST</em> be treated as the "organization-name".
</p>
<a name="Tags_as_Categories"></a><h3> <span class="mw-headline"> Tags as Categories </span></h3>
<p>Categories in hCard <em title="MAY in &#82;FC 2119 context" style="text-transform: lowercase; font-style: italic;" class="&#82;FC2119">MAY</em> be represented by tags with <a href="/wiki/rel-tag" title="rel-tag">rel-tag</a>. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.
</p>
<a name="type_subproperty_values"></a><h3> <span class="mw-headline"> type subproperty values </span></h3>
<p>The 'type' subproperty in particular takes different values depending on which property it is a subproperty of.  These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:
</p><p>vCard:
</p>
<pre>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</pre>
<p>hCard:
</p>
<pre>
&lt;span class=&quot;tel&quot;&gt;&lt;span class=&quot;type&quot;&gt;Home&lt;/span&gt; (&lt;span class=&quot;type&quot;&gt;pref&lt;/span&gt;erred):
 &lt;span class=&quot;value&quot;&gt;+1.415.555.1212&lt;/span&gt;
&lt;/span&gt;
</pre>
<p>This could be displayed as:
</p>
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<p><span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</p>
</div>
<a name="type_with_unspecified_value"></a><h4> <span class="mw-headline"> type with unspecified value </span></h4>
<p>When the type of a property is specified, and there is no explicit value specified, then everything in the property except for the type is considered the value of the property. E.g.
</p>
<pre>
&lt;span class=&quot;tel&quot;&gt;&lt;span class=&quot;type&quot;&gt;Home&lt;/span&gt; +1.415.555.1212&lt;/span&gt;
</pre>
<p>is equivalent to:
</p>
<pre>
&lt;span class=&quot;tel&quot;&gt;&lt;span class=&quot;type&quot;&gt;Home&lt;/span&gt;&lt;span class=&quot;value&quot;&gt; +1.415.555.1212&lt;/span&gt;&lt;/span&gt;
</pre>
<p>And thus the type is "home" and the value is "+1.415.555.1212".
</p>
<a name="adr_tel_email_types"></a><h4> <span class="mw-headline"> adr tel email types </span></h4>
<p>The following lists are <i>informative</i>. See <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a> sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values.  They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS.  types may be multivalued.
</p>
<ul><li> adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
</li><li> tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, <a href="http://flickr.com/photos/tags/carcellphone/" class="external text" title="http://flickr.com/photos/tags/carcellphone/" rel="nofollow">car</a>, isdn, pcs
</li><li> email type: INTERNET, x400, pref, "other IANA registered address types"
</li></ul>
<a name="XMDP_Profile"></a><h3> <span class="mw-headline"> XMDP Profile </span></h3>
<p>See <a href="/wiki/hcard-profile" title="hcard-profile">hcard-profile</a> for the <a href="http://gmpg.org/xmdp" class="external text" title="http://gmpg.org/xmdp" rel="nofollow">XMDP</a> profile of hCard which contains the above complete list of properties, with references to their <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a> definitions.
</p>
<a name="Parsing_Details"></a><h3> <span class="mw-headline"> Parsing Details </span></h3>
<p>See <a href="/wiki/hcard-parsing" title="hcard-parsing">hCard parsing</a>.
</p>
<a name="Examples"></a><h2> <span class="mw-headline"> Examples </span></h2>
<p>This section is informative.
</p>
<a name="Sample_vCard"></a><h3> <span class="mw-headline"> Sample vCard </span></h3>
<p>Here is a sample vCard:
</p>
<pre>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
END:VCARD
</pre>
<p>and an equivalent in hCard with various elements optimized appropriately.  See <a href="/wiki/hcard-example1-steps" title="hcard-example1-steps"> hCard Example 1</a> for the derivation. 
</p>
<pre>
&lt;div class=&quot;vcard&quot;&gt;
 &lt;a class=&quot;url fn&quot; href=&quot;http://tantek.com/&quot;&gt;Tantek Çelik&lt;/a&gt;
&lt;/div&gt;
</pre>
<p>This hCard might be displayed as:
</p>
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<p><a href="http://tantek.com/" class="external text" title="http://tantek.com/" rel="nofollow">Tantek Çelik</a>
</p>
</div>
<p>Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the &lt;head&gt; element.
</p>
<a name="Live_example"></a><h3> <span class="mw-headline">Live example</span></h3>
<p>Here is <a href="http://www.commerce.net/" class="external text" title="http://www.commerce.net/" rel="nofollow">Commercenet</a>'s contact details, as a live hCard which will be detected, on this page, by microformat parsing tools:
</p>
<div class="vcard">
<div class="fn org"><b>CommerceNet</b></div>
<div class="url"><b>http://www.commerce.net/</b></div>
<div class="adr"><b><span class="type">Work</span>:</b>
<div class="street-address"><b>169 University Avenue</b></div>
<p><span class="locality"><b>Palo Alto</b></span>, <span class="region"><b>CA</b></span>&nbsp;&nbsp;<span class="postal-code"><b>94301</b></span>
</p>
<div class="country-name"><b>USA</b></div>
</div>
<div class="tel"><b><span class="type">Work</span> +1-650-289-4040</b></div>
<div class="tel"><b><span class="type">Fax</span> +1-650-289-4041</b></div>
<div><b>Email <span class="email">info@commerce.net</span></b></div>
</div>
<p>The mark-up, emboldening omitted for clarity, with the following semantic improvements:
</p>
<ul><li> <code>abbr</code> to expand abbreviations
</li><li> hyperlinking the org name with the url
</li></ul>
<pre>
&lt;div class=&quot;vcard&quot;&gt;
  &lt;a class=&quot;fn org url&quot; href=&quot;http://www.commerce.net/&quot;&gt;CommerceNet&lt;/a&gt;
  &lt;div class=&quot;adr&quot;&gt;
    &lt;span class=&quot;type&quot;&gt;Work&lt;/span&gt;:
    &lt;div class=&quot;street-address&quot;&gt;169 University Avenue&lt;/div&gt;
    &lt;span class=&quot;locality&quot;&gt;Palo Alto&lt;/span&gt;,  
    &lt;abbr class=&quot;region&quot; title=&quot;California&quot;&gt;CA&lt;/abbr&gt;&nbsp;&nbsp;
    &lt;span class=&quot;postal-code&quot;&gt;94301&lt;/span&gt;
    &lt;div class=&quot;country-name&quot;&gt;USA&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class=&quot;tel&quot;&gt;
   &lt;span class=&quot;type&quot;&gt;Work&lt;/span&gt; +1-650-289-4040
  &lt;/div&gt;
  &lt;div class=&quot;tel&quot;&gt;
    &lt;span class=&quot;type&quot;&gt;Fax&lt;/span&gt; +1-650-289-4041
  &lt;/div&gt;
  &lt;div&gt;Email: 
   &lt;span class=&quot;email&quot;&gt;info@commerce.net&lt;/span&gt;
  &lt;/div&gt;
&lt;/div&gt;
</pre>
<a name="More_Examples"></a><h3> <span class="mw-headline"> More Examples </span></h3>
<p>See <a href="/wiki/hcard-examples" title="hcard-examples">hCard examples</a> for more examples, including all examples from vCard <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a> converted into hCard.
</p>
<a name="Buttons"></a><h2> <span class="mw-headline">Buttons</span></h2>
<p>You can use these buttons on pages with hCards. See <a href="/wiki/buttons#hCard" title="buttons">buttons#hCard</a> for any recent additions.
</p>
<ul><li> <img src="http://www.crowley.nl/images/hcard.png" alt="hcard.png" /> (mirror: <img src="http://www.davidjanes.com/images/mf_hcard.png" alt="mf_hcard.png" />)
</li><li> <img src="http://rbach.priv.at/2006/buttons/hcard.png" alt="hcard.png" />
</li><li> <img src="http://www.boogdesign.com/images/buttons/microformat_hcard.png" alt="microformat_hcard.png" />
</li><li> CSS-powered button, as evidenced at <a href="http://re-run.com/about/microformat-badges" class="external text" title="http://re-run.com/about/microformat-badges" rel="nofollow">microformat badges @ re-run</a>
</li></ul>
<a name="Examples_in_the_wild"></a><h2> <span class="mw-headline"> Examples in the wild </span></h2>
<p>This section is <b>informative</b>. The number of hCard examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a <a href="/wiki/hcard-examples-in-wild" title="hcard-examples-in-wild">separate page</a>.
</p><p>See <a href="/wiki/hcard-examples-in-wild" title="hcard-examples-in-wild">hCard Examples in the wild</a>.
</p>
<a name="Implementations"></a><h2> <span class="mw-headline"> Implementations </span></h2>
<p>This section is <b>informative</b>. The number of hCard implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a <a href="/wiki/hcard-implementations" title="hcard-implementations">separate page</a>.
</p><p>See <a href="/wiki/hcard-implementations" title="hcard-implementations">hCard Implementations</a>.
</p>
<a name="Copyright"></a><h2> <span class="mw-headline"> Copyright </span></h2>
<p>Per the public domain release on the authors' user pages (<a href="/wiki/User:Tantek" title="User:Tantek">Tantek Çelik</a>, <a href="/wiki/User:Brian" title="User:Brian">Brian Suda</a>) this specification is released into the public domain.
</p><p><strong>Public Domain Contribution Requirement</strong>. Since the author(s) released this work into the public domain, in order to maintain this work's public domain status, all contributors to this page agree to release their contributions to this page to the public domain as well. Contributors may indicate their agreement by adding the <a href="http://microformats.org/wiki/Template:public-domain-release" class="external text" title="http://microformats.org/wiki/Template:public-domain-release" rel="nofollow">public domain release template</a> to their user page per the <a href="http://microformats.org/wiki/Category:public_domain_license" class="external text" title="http://microformats.org/wiki/Category:public_domain_license" rel="nofollow">Voluntary Public Domain Declarations instructions</a>. Unreleased contributions may be reverted/removed.
</p>
<a name="Patents"></a><h2> <span class="mw-headline"> Patents </span></h2>
<p>This specification is subject to a royalty free patent policy, e.g. per the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/" class="external text" title="http://www.w3.org/Consortium/Patent-Policy-20040205/" rel="nofollow">W3C Patent Policy</a>, and  IETF <a href="http://www.ietf.org/rfc/rfc3667.txt" class="external text" title="http://www.ietf.org/rfc/rfc3667.txt" rel="nofollow">RFC3667</a> &amp; <a href="http://www.ietf.org/rfc/rfc3668.txt" class="external text" title="http://www.ietf.org/rfc/rfc3668.txt" rel="nofollow">RFC3668</a>.
</p>
<a name="References"></a><h2> <span class="mw-headline"> References </span></h2>
<a name="Normative_References"></a><h3> <span class="mw-headline"> Normative References </span></h3>
<ul><li> <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" class="external text" title="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" rel="nofollow">XHTML 1.0 SE</a>
</li><li> <a href="http://www.ietf.org/rfc/rfc2426.txt" class="external text" title="http://www.ietf.org/rfc/rfc2426.txt" rel="nofollow">vCard RFC2426</a>
</li><li> <a href="http://www.itu.int/rec/T-REC-E.123-200102-I/en" class="external text" title="http://www.itu.int/rec/T-REC-E.123-200102-I/en" rel="nofollow">ITU recommendation E.123</a> format of telephone numbers (chargeable document)
</li><li> <a href="/wiki/rfc-2119" title="rfc-2119">RFC 2119</a>
</li></ul>
<a name="Informative_References"></a><h3> <span class="mw-headline"> Informative References </span></h3>
<ul><li> <a href="/wiki/hcard-history" title="hcard-history">hCard history</a>
<ul><li> <a href="http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats" class="external text" title="http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats" rel="nofollow">FOO Camp 2004 Simple Semantic Formats presentation, 2004-09-10</a>
</li><li> <a href="http://tantek.com/log/2004/09.html#hcard" class="external text" title="http://tantek.com/log/2004/09.html#hcard" rel="nofollow">hCard term introduced and defined on the Web, 2004-09-30</a>
</li><li> Contributed from <a href="http://developers.technorati.com/wiki/hCard" class="external free" title="http://developers.technorati.com/wiki/hCard" rel="nofollow">http://developers.technorati.com/wiki/hCard</a> 2005-06-20
</li></ul>
</li><li> <a href="http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps" class="external text" title="http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps" rel="nofollow">X.520 in Postscript</a> (<a href="http://72.14.253.104/search?q=cache:FjqzsFu4h20J:www.dante.net/np/ds/osi/9594-6-X.520.A4.ps" class="external text" title="http://72.14.253.104/search?q=cache:FjqzsFu4h20J:www.dante.net/np/ds/osi/9594-6-X.520.A4.ps" rel="nofollow">HTMLization courtesy of Google Cache</a>) - vCard refers to ROLE as being "based on the X.520 Business Category explanatory attribute".
</li><li> <a href="http://www.w3.org/2002/12/cal/rfc2426" class="external text" title="http://www.w3.org/2002/12/cal/rfc2426" rel="nofollow">HTML reformatted version of RFC2426</a>
</li><li> <a href="http://w3.org/TR/REC-CSS1" class="external text" title="http://w3.org/TR/REC-CSS1" rel="nofollow">CSS1</a>
</li><li> <a href="http://www.w3.org/TR/xhtml11" class="external text" title="http://www.w3.org/TR/xhtml11" rel="nofollow">XHTML 1.1</a>
</li><li> <a href="http://en.wikipedia.org/wiki/E.123" class="external text" title="http://en.wikipedia.org/wiki/E.123" rel="nofollow">Wikipedia summary of ITU-T Recommendation E.123</a> - for "TEL" values.
</li><li> <a href="http://www.imc.org/pdi/" class="external text" title="http://www.imc.org/pdi/" rel="nofollow">Internet Mail Consortium Personal Data Interchange vCard and vCalendar</a>
</li><li> <a href="/wiki/iso-8601" title="iso-8601">ISO8601</a>
</li></ul>
<a name="Specifications_That_Use_hCard"></a><h4> <span class="mw-headline"> Specifications That Use hCard </span></h4>
<ul><li> <a href="/wiki/adr" title="adr">adr</a>
</li><li> <a href="/wiki/geo" title="geo">geo</a>
</li><li> <a href="/wiki/hcalendar" title="hcalendar">hCalendar</a>
</li><li> <a href="/wiki/hreview" title="hreview">hReview</a>
</li></ul>
<a name="Similar_Work"></a><h4> <span class="mw-headline"> Similar Work </span></h4>
<ul><li> <a href="http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement" class="external text" title="http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement" rel="nofollow">Atom PaceBetterPersonElement</a>
</li><li> <a href="http://www.jabber.org/jeps/jep-0054.html" class="external text" title="http://www.jabber.org/jeps/jep-0054.html" rel="nofollow">JEP-0054: vcard-temp</a>
</li></ul>
<a name="Inspiration_and_Acknowledgments"></a><h2> <span class="mw-headline"> Inspiration and Acknowledgments </span></h2>
<p>Thanks to: my good friend <a href="http://vadim.com/" class="external text" title="http://vadim.com/" rel="nofollow">Vadim</a> who introduced me to vCard <i>many</i> years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.
</p>
<a name="Notes_on_derivation_from_vCard"></a><h2> <span class="mw-headline"> Notes on derivation from vCard </span></h2>
<p>This section is <i>informative</i>.
</p>
<div id="Semantic_XHTML_Design_Principles">See: <a href="/wiki/hcard-design-methodology" title="hcard-design-methodology">hcard-design-methodology</a>.</div>
<a name="More_Semantic_Equivalents"></a><h3> <span class="mw-headline"> More Semantic Equivalents </span></h3>
<p>For some properties there are HTML elements which better match and convey their semantics.  The following properties SHOULD be encoded with the following HTML:
</p>
<ul><li> <code>URL</code> in vCard becomes  <code>&lt;a class="url" href="..."&gt;...&lt;/a&gt;</code> inside the element with <code>class="vcard"</code> in hCard.
</li><li> Similarly, <code>EMAIL</code> in vCard becomes <code>&lt;a class=&quot;email&quot; href=&quot;mailto:...&quot;&gt;...&lt;/a&gt;</code>
</li><li> <code>PHOTO</code> in vCard becomes <code>&lt;img class="photo" src="..." alt="Photo of ..." /&gt;</code> or <code>&lt;object class="photo" data="..." type="..."&gt;Photo of ...&lt;/object&gt;</code>
</li><li> <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.
</li></ul>
<a name="Singular_and_Plural_derivations"></a><h3> <span class="mw-headline"> Singular and Plural derivations </span></h3>
<p>The <a href="/wiki/hcard#Singular_vs._Plural_Properties" title="hcard">lists of singular and plural properties</a> have been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics.  See <a href="/wiki/hcard-singular-properties" title="hcard-singular-properties">hcard-singular-properties</a> for explanations.
</p>
<a name="Plural_Properties_Singularized"></a><h4> <span class="mw-headline"> Plural Properties Singularized </span></h4>
<p>Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.
</p>
<a name="Further_Reading"></a><h2> <span class="mw-headline"> Further Reading </span></h2>
<ul><li> <a href="http://www.digital-web.com/articles/microformats_primer/" class="external text" title="http://www.digital-web.com/articles/microformats_primer/" rel="nofollow">Digital Web Magazine: Microformats Primer</a> by Garrett Dimon has a good intro to hCard
</li><li> <a href="http://24ways.org/advent/practical-microformats-with-hcard" class="external text" title="http://24ways.org/advent/practical-microformats-with-hcard" rel="nofollow">Practical Microformats with hCard</a> by Drew McLellan
</li><li> <a href="http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/" class="external text" title="http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/" rel="nofollow">Local Search Engine Optimization using Microformats</a> by Chris Silver Smith
</li><li> <a href="http://thedredge.org/" class="external text" title="http://thedredge.org/" rel="nofollow">Andrew D. Hume</a> has written a blog post on <a href="http://usabletype.com/articles/2005/usable-microformats/" class="external text" title="http://usabletype.com/articles/2005/usable-microformats/" rel="nofollow">usable microformats</a> which discusses hCard
</li><li> <a href="http://www.thefutureoftheweb.com/blog/2006/1/hcard" class="external text" title="http://www.thefutureoftheweb.com/blog/2006/1/hcard" rel="nofollow">Jesse Skinner's introduction to hCard</a>
</li><li> <a href="http://blog.usweb.com/" class="external text" title="http://blog.usweb.com/" rel="nofollow">Shaun Shull's</a> great post on <a href="http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo" class="external text" title="http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo" rel="nofollow">How Microformats Affect SEO</a>, including his <strong class="selflink">hCard</strong> as an example.
</li><li> <a href="http://24ways.org/2006/styling-hcards-with-css" class="external text" title="http://24ways.org/2006/styling-hcards-with-css" rel="nofollow">24 Ways: Styling hCards with CSS</a> A 24 Ways article - John Allsopp on styling hCard using CSS 
</li><li> See also <a href="http://www.technorati.com/cosmos/referer.html" class="external text" title="http://www.technorati.com/cosmos/referer.html" rel="nofollow">blogs discussing this page</a> and the <a href="http://technorati.com/tags/hcard" class="external text" title="http://technorati.com/tags/hcard" rel="nofollow">hCard tag</a>
</li><li> <a href="http://www.rfc-editor.org/rfc/rfc4770.txt" class="external text" title="http://www.rfc-editor.org/rfc/rfc4770.txt" rel="nofollow">RFC 4770 Extensions for Instant Messaging</a>
</li><li> <a href="http://ungeekdapo.wordpress.com/2008/04/30/a-real-life-use-case-of-microformat-hcard-in-action/" class="external text" title="http://ungeekdapo.wordpress.com/2008/04/30/a-real-life-use-case-of-microformat-hcard-in-action/" rel="nofollow">A real life use case of Microformat hCard in action</a> by Bob Ngu
</li><li> <a href="http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard/" class="external text" title="http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard/" rel="nofollow">Getting Semantic With Microformats, Part 3: hCard</a> by <a href="http://www.ablognotlimited.com/" class="external text" title="http://www.ablognotlimited.com/" rel="nofollow">Emily Lewis</a>
</li><li> <a href="http://www.peachpit.com/guides/content.aspx?g=webdesign&amp;seqNum=354" class="external text" title="http://www.peachpit.com/guides/content.aspx?g=webdesign&amp;seqNum=354" rel="nofollow">Microformats: The Fine Art of Markup: hCard</a> by <a href="http://www.stuffandnonsense.co.uk/" class="external text" title="http://www.stuffandnonsense.co.uk/" rel="nofollow">Andy Clarke</a>
</li></ul>
<a name="Related_Pages"></a><h2> <span class="mw-headline"> Related Pages </span></h2>
<ul><li> <strong class="selflink">hCard</strong>
</li><li> <a href="/wiki/hcard-cheatsheet" title="hcard-cheatsheet">hCard cheatsheet</a> - hCard properties
</li><li> <a href="http://microformats.org/code/hcard/creator" class="external text" title="http://microformats.org/code/hcard/creator" rel="nofollow">hCard creator</a> (<a href="/wiki/hcard-creator-feedback" title="hcard-creator-feedback">feedback</a>) - create your own hCard.
</li><li> <a href="/wiki/hcard-authoring" title="hcard-authoring">hCard authoring</a> - learn how to add hCard markup to your existing contact info.
</li><li> <a href="/wiki/hcard-examples" title="hcard-examples">hCard examples</a> - example usage of various classes within hCard.
</li><li> <a href="/wiki/hcard-examples-in-wild" title="hcard-examples-in-wild">hCard examples in the wild</a> - an on-going list of websites which use hCards.
</li><li> <a href="/wiki/hcard-supporting-user-profiles" title="hcard-supporting-user-profiles">hcard-supporting-user-profiles</a> - sites with user profiles marked up with hCard - a very common example.
</li><li> <a href="/wiki/hcard-faq" title="hcard-faq">hCard FAQ</a> - if you have any questions about hCard, check here.
</li><li> <a href="/wiki/hcard-implementations" title="hcard-implementations">hCard implementations</a> - websites or tools which either generate or parse hCards.
</li><li> <a href="/wiki/hcard-implied" title="hcard-implied">hcard-implied</a> - a proposal to create a alternative method of marking up a simple hCard
</li><li> <a href="/wiki/hcard-parsing" title="hcard-parsing">hCard parsing</a> - normative details of how to parse hCards.
</li><li> <a href="/wiki/hcard-user-interface" title="hcard-user-interface">hcard-user-interface</a> - techniques and issues surrounding user-interfaces to author, publish, and display hCards.
</li><li> <a href="/wiki/hcard-profile" title="hcard-profile">hCard profile</a> - the XMDP profile for hCard
</li><li><a href="/wiki/hcard-singular-properties" title="hcard-singular-properties">hCard singular properties</a> - an explanation of the list of singular properties in hCard.
</li><li> <a href="/wiki/hcard-tests" title="hcard-tests">hCard tests</a> - a wiki page with actual embedded hCards to try parsing.
</li><li> <a href="/wiki/hcard-advocacy" title="hcard-advocacy">hCard advocacy</a> - encourage others to use hCard
</li><li> <a href="/wiki/hCard-to-do" class="mw-redirect" title="hCard-to-do">hCard "to do"</a> - jobs to do
</li></ul>
<p>The hCard specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.
</p>
<ul><li> <a href="/wiki/hcard-brainstorming" title="hcard-brainstorming">hCard brainstorming</a> - brainstorms and other explorations relating to hCard.
<ul><li> <a href="/wiki/hcard-parsing-brainstorming" title="hcard-parsing-brainstorming">hcard-parsing-brainstorming</a> - brainstorming specific to parsing of hCard
</li><li> <a href="/wiki/geo-brainstorming" title="geo-brainstorming">geo brainstorming</a>
</li></ul>
</li><li> <a href="/wiki/hcard-feedback" title="hcard-feedback">hCard feedback</a> - general feedback (as opposed to specific issues).
</li><li> <a href="/wiki/hcard-issues" title="hcard-issues">hCard issues</a> - specific issues with the specification.
</li><li> <a href="/wiki/vcard-errata" title="vcard-errata">vCard errata</a> - corrections to the vCard specification, which underlies hCard.
</li><li> <a href="/wiki/vcard-suggestions" title="vcard-suggestions">vCard suggestions</a> - suggested improvements to the vCard specification.
</li></ul>

<!-- 
NewPP limit report
Preprocessor node count: 247/1000000
Post-expand include size: 9303/2097152 bytes
Template argument size: 0/2097152 bytes
Expensive parser function count: 0/100
-->
<div class="printfooter">
Retrieved from "<a href="http://microformats.org/wiki/hcard">http://microformats.org/wiki/hcard</a>"</div>
		</div>	
		
			        <h2>Categories</h2>
		    <div id="category-links">
		        <ul>
		        		            <li><a rel="tag" href="/wiki/Category:Specifications">
		                Specifications		            </a></li>
		        		            <li><a rel="tag" href="/wiki/Category:hCard">
		                hCard		            </a></li>
		        		        </ul>
		    </div>		        
				
                    <div class="vevent last-modified">
                <span class="summary">
                    ‘<a rel="bookmark" class="url uid" href="/wiki/index.php?title=hcard&amp;oldid=37804">hCard</a>’
                    was last modified</span>:
                                    <span class="dtstart updated">2009-01-31T18:12:00P</span>
            </div>
        
        <div id="content-controls">
    		<h2>Views</h2>
    		<ul>
                		    <li id="ca-viewsource"><a href="/wiki/index.php?title=hcard&amp;action=edit" title="This page is protected.&#10;You can view its source. [e]" accesskey="e">View source</a></li>
                		    <li id="ca-history"><a href="/wiki/index.php?title=hcard&amp;action=history" title="Past versions of this page. [h]" accesskey="h">History</a></li>
                		</ul>
    	</div>

	</div>
	
<div id="sidebar">


	<div class="box" id="p-Microformats_Wiki">
		<h3>Microformats Wiki</h3>
		<ul class="box-inner">
			<li id="n-Front-Page"><a href="/wiki/Main_Page">Front Page</a></li>
			<li id="n-recentchanges"><a href="/wiki/Special:RecentChanges" title="The list of recent changes in the wiki. [r]" accesskey="r">Recent changes</a></li>
			<li id="n-Events"><a href="/wiki/Microformats_Wiki:Current_events">Events</a></li>
			<li id="n-help"><a href="/wiki/Help:Contents" title="The place to find out.">Help</a></li>
		</ul>
	</div>
	
	
	<div class="box" id="p-tb">
		<h3>Toolbox</h3>
		<ul class="box-inner">
				<li id="t-whatlinkshere"><a href="/wiki/Special:WhatLinksHere/hcard" title="List of all wiki pages that link here [j]" accesskey="j">What links here</a></li>
				<li id="t-recentchangeslinked"><a href="/wiki/Special:RecentChangesLinked/hcard" title="Recent changes in pages linked from this page [k]" accesskey="k">Related changes</a></li>
<li id="t-specialpages"><a href="/wiki/Special:SpecialPages" title="List of all special pages [q]" accesskey="q">Special pages</a></li>
				<li id="t-print"><a href="/wiki/index.php?title=hcard&amp;printable=yes" title="Printable version of this page [p]" accesskey="p">Printable version</a></li>				<li id="t-permalink"><a href="/wiki/index.php?title=hcard&amp;oldid=37804" title="Permanent link to this version of the page">Permanent link</a></li>		</ul>
	</div>



	<div class="box" id="user-box">
	    	    <h3>Hey! You're not logged in</h3>
		<ul class="box-inner">
        		    <li id="pt-login"><a href="/wiki/index.php?title=Special:UserLogin&amp;returnto=hcard" title="You are encouraged to log in, it is not mandatory however. [o]" accesskey="o">Log in / create account</a></li>
                
        
        
		</ul>
	</div>

</div><!-- end of the sidebar -->

<div id="footer">


    <address class="vcard">
        The content of this wiki is the combined effort of the
        <a class="fn org url" href="http://microformats.org">
            microformats community
        </a>.
    </address>

	<ul>
    				<li id="about"><a href="/wiki/Microformats_Wiki:About" title="Microformats Wiki:About">About Microformats Wiki</a></li>
				<li id="disclaimer"><a href="/wiki/Microformats_Wiki:General_disclaimer" title="Microformats Wiki:General disclaimer">Disclaimers</a></li>
        <li>Powered by <a href="http://mediawiki.org">MediaWiki</a></li>
	</ul>
</div>

		<script type="text/javascript">if (window.runOnloadHook) runOnloadHook();</script>
<!-- Served in 1.390 secs. --><script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
<script type="text/javascript">
_uacct = "UA-1889385-1";
urchinTracker();
</script>


</body></html>
